Stowing worker user interface

ABSTRACT

The present disclosure provides systems and methods for stowing products, comprising a memory storing instructions and a processor configured to execute the instructions to receive a tote identifier associated with a tote containing at least one product for stowing, predict, based on the tote identifier, a location for stowing the product, and provide a location recommendation for stowing the product based on the predicted location. The processor is configured to receive a product identifier, a location identifier, and a quantity of the product to be stowed. The processor is configured to modify a database to assign the location identifier and the quantity to the product identifier, receive a notification of a stowing error associated with the tote identifier, modify the database to assign the stowing error to the tote identifier, and automatically report the stowing error.

TECHNICAL FIELD

The present disclosure generally relates to computerized systems andmethods for stowing products. In particular, embodiments of the presentdisclosure relate to inventive and unconventional systems related tostowing products by predicting locations within a fulfillment center tostow the products and automatically reporting any stowing errorsassociated with the products.

BACKGROUND

Various systems and methods exist for stowing inbound products andreporting any errors that may arise while stowing the inbound products.For example, as inbound products arrive at fulfillment centers, stowingworkers manually scan identifiers associated with the products, such asstocking keeping units (SKUs) and manually fill out reports for eacherror, such as product damage, barcode damage, incorrect products, orthe like. Then, the stowing workers gather the inbound products witherrors and deliver these products back to the manufacturers forreshipment. While these conventional systems and methods may beeffective in reporting stowing errors, there has yet to be an efficientmethod for stowing products that efficiently provides locationrecommendation for stowing the products once the products are scannedand automatically reports any stowing errors to be resolved.

Errors that arise during stowing inbound products can significantlydelay the shipment and delivery of products to customers. As oneexample, stowing workers may make mistakes in calculating the quantityof inbound products and, as such, physical quantity of a certain productmay be different from the expected quantity of the product. Moreover,stowing errors may also arise at the manufacturers. For example, themanufacturers may make mistakes when sending inbound products tofulfillment centers for stowing. For example, manufacturers may sendless than an expected quantity of a certain product. As such, when thestowing worker is stowing the product in a fulfillment center, thephysical quantity of the product may not match the expected quantity ofthe product. Since errors that arise during stowing inbound products areinevitable, it is crucial that the stowing errors are reported andresolved quickly and efficiently in order to reduce delays in shipmentand delivery of products to customers.

In addition, conventional systems and methods for stowing inboundproducts stow products in fixed locations within a fulfillment center.For example, conventional systems and methods may be configured todesignate different types of products to a predetermined location withinthe fulfillment center for stowing. Furthermore, based on certainrestriction rules, conventional systems and methods may determine alocation within the fulfillment center for stowing products. By way ofexample, based on the restrictions rules, all products with the same SKUmay need to be placed in a fixed location within the fulfillment center,and all products with the same expiration date may need to be placed inanother fixed location within the fulfillment center. While providing afixed location for stowing each product may be helpful in organizing theinbound products within the fulfillment center, this may significantlydelay the shipment and delivery of products to customers. Especially forlarge companies, fulfillment centers and warehouses may be extremelylarge, and thus, it may take increase the time it takes to stow eachproduct in its fixed location within the fulfillment center.

Therefore, there is a need for improved systems and methods for stowingproducts. In particular, there is a need for improved systems andmethods for stowing products that is capable of predicting a locationwithin the fulfillment center for stowing inbound products when anidentifier is scanned. In addition, there is a need for improved systemsand methods for stowing products that receives notifications of stowingerrors associated with an inbound product and automatically reportsstowing errors to be resolved to a remote device.

SUMMARY

One aspect of the present disclosure is directed to acomputer-implemented system for stowing products. The system maycomprise a memory storing instructions and at least one processorconfigured to execute the instructions. The at least one processor maybe configured to execute the instructions to receive, from a user deviceassociated with a user, a tote identifier associated with a totecontaining at least one product for stowing, predict, based on the toteidentifier, a location for stowing the at least one product contained inthe tote, provide, to the user device, a location recommendation forstowing the at least one product contained in the tote based on thepredicted location, receive, from the user device, a product identifierassociated with the at least one product, a location identifierassociated with a position at which the at least one product is to bestowed, and a quantity of the at least one product to be stowed, andmodify a database to assign the location identifier and the quantity tothe product identifier. The at least one processor may be configured toexecute the instructions to receive, from the user device, anotification of a stowing error associated with the tote identifier,modify a database to assign the stowing error to the tote identifier,and automatically report the stowing error to a remote device.

In some embodiments, the product identifier associated with the at leastone product may comprise a stock keeping unit (SKU) associated with theat least one product. In some embodiments, predicting the location forstowing the at least one product contained in the tote may comprisedetermining a location of the user device, determining empty locationswithin a fulfillment center capable of receiving the at least oneproduct, and selecting, among the empty locations, an empty locationclosest to the location of the user device as the location for stowingthe at least one product. In some embodiments, when the tote identifieris scanned, the at least one processor is further configured to executethe instructions to send a cause of the stowing error for display to theuser device.

In some embodiments, the stowing error may comprise at least one of anoverage or a shortage. When a physical quantity of the at least oneproduct is less than an expected quantity of the at least one product,the stowing error may comprise shortage. When a physical quantity of theat least one product is greater than an expected quantity of the atleast one product, the stowing error may comprise overage. When thestowing error comprises overage, the at least one processor may beconfigured to execute the instructions to determine a cause for theoverage, the cause for the overage comprising at least one of a productdamage, a barcode damage, or an incorrect product. When the stowingerror comprises shortage, the at least one processor may be configuredto execute the instructions to request, via the user device, adifference between the physical quantity of the at least one product andthe expected quantity of the at least one product, and store thedifference in the database. When the cause for the overage comprises atleast one of the product damage or the barcode damage, the at least oneprocessor is further configured to execute the instructions to provide,via the user device, a location recommendation for transferring at leastone product with at least one of the product damage or the barcodedamage.

Another aspect of the present disclosure is directed to acomputer-implemented method for stowing products. The method maycomprise receiving, from a user device associated with a user, a toteidentifier associated with a tote containing at least one product forstowing, predicting, based on the tote identifier, a location forstowing the at least one product contained in the tote, providing, tothe user device, a location recommendation for stowing the at least oneproduct contained in the tote based on the predicted location,receiving, from the user device, a product identifier associated withthe at least one product, a location identifier associated with aposition at which the at least one product is to be stowed, and aquantity of the at least one product to be stowed, and modifying adatabase to assign the location identifier and the quantity to theproduct identifier. The method may also comprise receiving, from theuser device, a notification of a stowing error associated with the toteidentifier, modifying a database to assign the stowing error to the toteidentifier, and automatically reporting the stowing error to a remotedevice.

In some embodiments, predicting the location for stowing the at leastone product contained in the tote may comprise determining a location ofthe user device, determining empty locations within a fulfillment centercapable of receiving the at least one product, and selecting, among thedetermined empty locations, an empty location closest to the location ofthe user device as the location for stowing the at least one product.The method may further comprise sending a cause of the stowing error fordisplay displaying to the user device.

In some embodiments, the stowing error may comprise at least one of anoverage or a shortage. When a physical quantity of the at least oneproduct is less than an expected quantity of the at least one product,the stowing error may comprise shortage. When a physical quantity of theat least one product is greater than an expected quantity of the atleast one product, the stowing error may comprise overage. When thestowing error comprises overage, the method may further comprisedetermining a cause for the overage, the cause for the overagecomprising at least one of a product damage, a barcode damage, or anincorrect product. When the stowing error comprises shortage, the methodmay further comprise requesting, via the user device, a differencebetween the physical quantity of the at least one product and theexpected quantity of the at least one product, and storing thedifference in the database. When the cause for the overage comprises atleast one of the product damage or the barcode damage, the method mayfurther comprise providing, via the user device, a locationrecommendation for transferring at least one product with at least oneof the product damage or the barcode damage.

Yet another aspect of the present disclosure is directed to acomputer-implemented system for stowing products. The system maycomprise a memory storing instructions and at least one processorconfigured to execute the instructions. The at least one processor maybe configured to execute the instructions to receive, from a user deviceassociated with a user, a tote identifier associated with a totecontaining at least one product for stowing, predict, based on the toteidentifier, a location for stowing the at least one product contained inthe tote, provide, to the user device, a location recommendation forstowing the at least one product contained in the tote based on thepredicted location, receive, from the user device, a product identifierassociated with the at least one product, a location identifierassociated with a position at which the at least one product is to bestowed, and a quantity of the at least one product to be stowed, andmodify a database to assign the location identifier and the quantity tothe product identifier. The at least one processor may be configured toexecute the instructions to receive, from the user device, anotification of a stowing error associated with the tote identifier,modify a database to assign the stowing error to the tote identifier,and automatically report the stowing error to a remote device.

In some embodiments, predicting the location for stowing the at leastone product contained in the tote may comprise determining a location ofthe user device, determining empty locations within a fulfillment centerthat is capable of receiving the at least one product, and selecting,among the determined empty locations, an empty location closest to thelocation of the user device as the location for stowing the at least oneproduct. In some embodiments, the stowing error may comprise at leastone of an overage or a shortage. When the stowing error comprisesoverage, the at least one processor may be configured to execute theinstructions to determine a cause for the overage, the cause for theoverage comprising at least one of a product damage or a barcode damage,and provide, via the user device, a location recommendation fortransferring at least one product with at least one of the productdamage or the barcode damage. When the stowing error comprises shortage,the at least one processor may be configured to execute the instructionsto request, via the user device, a difference between the physicalquantity of the at least one product and the expected quantity of the atleast one product, and store the difference in the database.

Other systems, methods, and computer-readable media are also discussedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations, consistent with the disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) that includes one ormore search results satisfying a search request along with interactiveuser interface elements, consistent with the disclosed embodiments.

FIG. 1C depicts a sample Single Display Page (SDP) that includes aproduct and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 1D depicts a sample Cart page that includes items in a virtualshopping cart along with interactive user interface elements, consistentwith the disclosed embodiments.

FIG. 1E depicts a sample Order page that includes items from the virtualshopping cart along with information regarding purchase and shipping,along with interactive user interface elements, consistent with thedisclosed embodiments.

FIG. 2 is a diagrammatic illustration of an exemplary fulfillment centerconfigured to utilize disclosed computerized systems, consistent withthe disclosed embodiments.

FIG. 3 is a schematic block diagram illustrating an exemplary embodimentof a system comprising a stowing error monitoring system for stowingproducts, consistent with the disclosed embodiments.

FIG. 4A is a diagrammatic illustration of an exemplary graphical userinterface on a user device configured to facilitate stowing products,consistent with the disclosed embodiments.

FIG. 4B is another diagrammatic illustration of the exemplary graphicaluser interface of FIG. 4A, consistent with the disclosed embodiments.

FIG. 4C is another diagrammatic illustration of the exemplary graphicaluser interface of FIG. 4A, consistent with the disclosed embodiments.

FIG. 5A is a diagrammatic illustration of another exemplary graphicaluser interface on a user device configured to facilitate reporting astowing error, consistent with the disclosed embodiments.

FIG. 5B is another diagrammatic illustration of the exemplary graphicaluser interface of FIG. 5A, consistent with the disclosed embodiments.

FIG. 5C is another diagrammatic illustration of the exemplary graphicaluser interface of FIG. 5A, consistent with the disclosed embodiments.

FIG. 6 is an exemplary database configured to store informationassociated with products for stowing, consistent with the disclosedembodiments.

FIG. 7 is a flowchart illustrating an exemplary embodiment of a methodfor stowing products, consistent with the disclosed embodiments.

FIG. 8 is a flowchart illustrating another exemplary embodiment of amethod for stowing products, consistent with the disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents and steps illustrated in the drawings, and the illustrativemethods described herein may be modified by substituting, reordering,removing, or adding steps to the disclosed methods. Accordingly, thefollowing detailed description is not limited to the disclosedembodiments and examples. Instead, the proper scope of the invention isdefined by the appended claims.

Embodiments of the present disclosure are directed to systems andmethods configured for stowing inbound products and reporting stowingerrors.

Referring to FIG. 1A, a schematic block diagram 100 illustrating anexemplary embodiment of a system comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations is shown. As illustrated in FIG. 1A, system 100 may include avariety of systems, each of which may be connected to one another viaone or more networks. The systems may also be connected to one anothervia a direct connection, for example, using a cable. The depictedsystems include a shipment authority technology (SAT) system 101, anexternal front end system 103, an internal front end system 105, atransportation system 107, mobile devices 107A, 107B, and 107C, sellerportal 109, shipment and order tracking (SOT) system 111, fulfillmentoptimization (FO) system 113, fulfillment messaging gateway (FMG) 115,supply chain management (SCM) system 117, warehouse management system119, mobile devices 119A, 119B, and 119C (depicted as being inside offulfillment center (FC) 200), 3^(rd) party fulfillment systems 121A,121B, and 121C, fulfillment center authorization system (FC Auth) 123,and labor management system (LMS) 125.

SAT system 101, in some embodiments, may be implemented as a computersystem that monitors order status and delivery status. For example, SATsystem 101 may determine whether an order is past its Promised DeliveryDate (PDD) and may take appropriate action, including initiating a neworder, reshipping the items in the non-delivered order, canceling thenon-delivered order, initiating contact with the ordering customer, orthe like. SAT system 101 may also monitor other data, including output(such as a number of packages shipped during a particular time period)and input (such as the number of empty cardboard boxes received for usein shipping). SAT system 101 may also act as a gateway between differentdevices in system 100, enabling communication (e.g., usingstore-and-forward or other techniques) between devices such as externalfront end system 103 and FO system 113.

External front end system 103, in some embodiments, may be implementedas a computer system that enables external users to interact with one ormore systems in system 100. For example, in embodiments where system 100enables the presentation of systems to enable users to place an orderfor an item, external front end system 103 may be implemented as a webserver that receives search requests, presents item pages, and solicitspayment information. For example, external front end system 103 may beimplemented as a computer or computers running software such as theApache HTTP Server, Microsoft Internet Information Services (IIS),NGINX, or the like. In other embodiments, external front end system 103may run custom web server software designed to receive and processrequests from external devices (e.g., mobile device 102A or computer102B), acquire information from databases and other data stores based onthose requests, and provide responses to the received requests based onacquired information.

In some embodiments, external front end system 103 may include one ormore of a web caching system, a database, a search system, or a paymentsystem. In one aspect, external front end system 103 may comprise one ormore of these systems, while in another aspect, external front endsystem 103 may comprise interfaces (e.g., server-to-server,database-to-database, or other network connections) connected to one ormore of these systems.

An illustrative set of steps, illustrated by FIGS. 1B, 1C, 1D, and 1E,will help to describe some operations of external front end system 103.External front end system 103 may receive information from systems ordevices in system 100 for presentation and/or display. For example,external front end system 103 may host or provide one or more web pages,including a Search Result Page (SRP) (e.g., FIG. 1B), a Single DetailPage (SDP) (e.g., FIG. 1C), a Cart page (e.g., FIG. 1D), or an Orderpage (e.g., FIG. 1E). A user device (e.g., using mobile device 102A orcomputer 102B) may navigate to external front end system 103 and requesta search by entering information into a search box. External front endsystem 103 may request information from one or more systems in system100. For example, external front end system 103 may request informationfrom FO System 113 that satisfies the search request. External front endsystem 103 may also request and receive (from FO System 113) a PromisedDelivery Date or “PDD” for each product included in the search results.The PDD, in some embodiments, may represent an estimate of when apackage containing the product will arrive at the user's desiredlocation or a date by which the product is promised to be delivered atthe user's desired location if ordered within a particular period oftime, for example, by the end of the day (11:59 PM). (PDD is discussedfurther below with respect to FO System 113.)

External front end system 103 may prepare an SRP (e.g., FIG. 1B) basedon the information. The SRP may include information that satisfies thesearch request. For example, this may include pictures of products thatsatisfy the search request. The SRP may also include respective pricesfor each product, or information relating to enhanced delivery optionsfor each product, PDD, weight, size, offers, discounts, or the like.External front end system 103 may send the SRP to the requesting userdevice (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clickingor tapping a user interface, or using another input device, to select aproduct represented on the SRP. The user device may formulate a requestfor information on the selected product and send it to external frontend system 103. In response, external front end system 103 may requestinformation related to the selected product. For example, theinformation may include additional information beyond that presented fora product on the respective SRP. This could include, for example, shelflife, country of origin, weight, size, number of items in package,handling instructions, or other information about the product. Theinformation could also include recommendations for similar products(based on, for example, big data and/or machine learning analysis ofcustomers who bought this product and at least one other product),answers to frequently asked questions, reviews from customers,manufacturer information, pictures, or the like.

External front end system 103 may prepare an SDP (Single Detail Page)(e.g., FIG. 1C) based on the received product information. The SDP mayalso include other interactive elements such as a “Buy Now” button, a“Add to Cart” button, a quantity field, a picture of the item, or thelike. The SDP may further include a list of sellers that offer theproduct. The list may be ordered based on the price each seller offerssuch that the seller that offers to sell the product at the lowest pricemay be listed at the top. The list may also be ordered based on theseller ranking such that the highest ranked seller may be listed at thetop. The seller ranking may be formulated based on multiple factors,including, for example, the seller's past track record of meeting apromised PDD. External front end system 103 may deliver the SDP to therequesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the productinformation. Upon receiving the SDP, the user device may then interactwith the SDP. For example, a user of the requesting user device mayclick or otherwise interact with a “Place in Cart” button on the SDP.This adds the product to a shopping cart associated with the user. Theuser device may transmit this request to add the product to the shoppingcart to external front end system 103.

External front end system 103 may generate a Cart page (e.g., FIG. 1D).The Cart page, in some embodiments, lists the products that the user hasadded to a virtual “shopping cart.” A user device may request the Cartpage by clicking on or otherwise interacting with an icon on the SRP,SDP, or other pages. The Cart page may, in some embodiments, list allproducts that the user has added to the shopping cart, as well asinformation about the products in the cart such as a quantity of eachproduct, a price for each product per item, a price for each productbased on an associated quantity, information regarding PDD, a deliverymethod, a shipping cost, user interface elements for modifying theproducts in the shopping cart (e.g., deletion or modification of aquantity), options for ordering other product or setting up periodicdelivery of products, options for setting up interest payments, userinterface elements for proceeding to purchase, or the like. A user at auser device may click on or otherwise interact with a user interfaceelement (e.g., a button that reads “Buy Now”) to initiate the purchaseof the product in the shopping cart. Upon doing so, the user device maytransmit this request to initiate the purchase to external front endsystem 103.

External front end system 103 may generate an Order page (e.g., FIG. 1E)in response to receiving the request to initiate a purchase. The Orderpage, in some embodiments, re-lists the items from the shopping cart andrequests input of payment and shipping information. For example, theOrder page may include a section requesting information about thepurchaser of the items in the shopping cart (e.g., name, address, e-mailaddress, phone number), information about the recipient (e.g., name,address, phone number, delivery information), shipping information(e.g., speed/method of delivery and/or pickup), payment information(e.g., credit card, bank transfer, check, stored credit), user interfaceelements to request a cash receipt (e.g., for tax purposes), or thelike. External front end system 103 may send the Order page to the userdevice.

The user device may enter information on the Order page and click orotherwise interact with a user interface element that sends theinformation to external front end system 103. From there, external frontend system 103 may send the information to different systems in system100 to enable the creation and processing of a new order with theproducts in the shopping cart.

In some embodiments, external front end system 103 may be furtherconfigured to enable sellers to transmit and receive informationrelating to orders.

Internal front end system 105, in some embodiments, may be implementedas a computer system that enables internal users (e.g., employees of anorganization that owns, operates, or leases system 100) to interact withone or more systems in system 100. For example, in embodiments wherenetwork 101 enables the presentation of systems to enable users to placean order for an item, internal front end system 105 may be implementedas a web server that enables internal users to view diagnostic andstatistical information about orders, modify item information, or reviewstatistics relating to orders. For example, internal front end system105 may be implemented as a computer or computers running software suchas the Apache HTTP Server, Microsoft Internet Information Services(IIS), NGINX, or the like. In other embodiments, internal front endsystem 105 may run custom web server software designed to receive andprocess requests from systems or devices depicted in system 100 (as wellas other devices not depicted), acquire information from databases andother data stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, internal front end system 105 may include one ormore of a web caching system, a database, a search system, a paymentsystem, an analytics system, an order monitoring system, or the like. Inone aspect, internal front end system 105 may comprise one or more ofthese systems, while in another aspect, internal front end system 105may comprise interfaces (e.g., server-to-server, database-to-database,or other network connections) connected to one or more of these systems.

Transportation system 107, in some embodiments, may be implemented as acomputer system that enables communication between systems or devices insystem 100 and mobile devices 107A-107C. Transportation system 107, insome embodiments, may receive information from one or more mobiledevices 107A-107C (e.g., mobile phones, smart phones, PDAs, or thelike). For example, in some embodiments, mobile devices 107A-107C maycomprise devices operated by delivery workers. The delivery workers, whomay be permanent, temporary, or shift employees, may utilize mobiledevices 107A-107C to effect delivery of packages containing the productsordered by users. For example, to deliver a package, the delivery workermay receive a notification on a mobile device indicating which packageto deliver and where to deliver it. Upon arriving at the deliverylocation, the delivery worker may locate the package (e.g., in the backof a truck or in a crate of packages), scan or otherwise capture dataassociated with an identifier on the package (e.g., a barcode, an image,a text string, an RFID tag, or the like) using the mobile device, anddeliver the package (e.g., by leaving it at a front door, leaving itwith a security guard, handing it to the recipient, or the like). Insome embodiments, the delivery worker may capture photo(s) of thepackage and/or may obtain a signature using the mobile device. Themobile device may send information to transportation system 107including information about the delivery, including, for example, time,date, GPS location, photo(s), an identifier associated with the deliveryworker, an identifier associated with the mobile device, or the like.Transportation system 107 may store this information in a database (notpictured) for access by other systems in system 100. Transportationsystem 107 may, in some embodiments, use this information to prepare andsend tracking data to other systems indicating the location of aparticular package.

In some embodiments, certain users may use one kind of mobile device(e.g., permanent workers may use a specialized PDA with custom hardwaresuch as a barcode scanner, stylus, and other devices) while other usersmay use other kinds of mobile devices (e.g., temporary or shift workersmay utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user witheach device. For example, transportation system 107 may store anassociation between a user (represented by, e.g., a user identifier, anemployee identifier, or a phone number) and a mobile device (representedby, e.g., an International Mobile Equipment Identity (IMEI), anInternational Mobile Subscription Identifier (IMSI), a phone number, aUniversal Unique Identifier (UUID), or a Globally Unique Identifier(GUID)). Transportation system 107 may use this association inconjunction with data received on deliveries to analyze data stored inthe database in order to determine, among other things, a location ofthe worker, an efficiency of the worker, or a speed of the worker.

Seller portal 109, in some embodiments, may be implemented as a computersystem that enables sellers or other external entities to electronicallycommunicate with one or more systems in system 100. For example, aseller may utilize a computer system (not pictured) to upload or provideproduct information, order information, contact information, or thelike, for products that the seller wishes to sell through system 100using seller portal 109.

Shipment and order tracking system 111, in some embodiments, may beimplemented as a computer system that receives, stores, and forwardsinformation regarding the location of packages containing productsordered by customers (e.g., by a user using devices 102A-102B). In someembodiments, shipment and order tracking system 111 may request or storeinformation from web servers (not pictured) operated by shippingcompanies that deliver packages containing products ordered bycustomers.

In some embodiments, shipment and order tracking system 111 may requestand store information from systems depicted in system 100. For example,shipment and order tracking system 111 may request information fromtransportation system 107. As discussed above, transportation system 107may receive information from one or more mobile devices 107A-107C (e.g.,mobile phones, smart phones, PDAs, or the like) that are associated withone or more of a user (e.g., a delivery worker) or a vehicle (e.g., adelivery truck). In some embodiments, shipment and order tracking system111 may also request information from warehouse management system (WMS)119 to determine the location of individual products inside of afulfillment center (e.g., fulfillment center 200). Shipment and ordertracking system 111 may request data from one or more of transportationsystem 107 or WMS 119, process it, and present it to a device (e.g.,user devices 102A and 102B) upon request.

Fulfillment optimization (FO) system 113, in some embodiments, may beimplemented as a computer system that stores information for customerorders from other systems (e.g., external front end system 103 and/orshipment and order tracking system 111). FO system 113 may also storeinformation describing where particular items are held or stored. Forexample, certain items may be stored only in one fulfillment center,while certain other items may be stored in multiple fulfillment centers.In still other embodiments, certain fulfillment centers may be designedto store only a particular set of items (e.g., fresh produce or frozenproducts). FO system 113 stores this information as well as associatedinformation (e.g., quantity, size, date of receipt, expiration date,etc.).

FO system 113 may also calculate a corresponding PDD (promised deliverydate) for each product. The PDD, in some embodiments, may be based onone or more factors. For example, FO system 113 may calculate a PDD fora product based on a past demand for a product (e.g., how many timesthat product was ordered during a period of time), an expected demandfor a product (e.g., how many customers are forecast to order theproduct during an upcoming period of time), a network-wide past demandindicating how many products were ordered during a period of time, anetwork-wide expected demand indicating how many products are expectedto be ordered during an upcoming period of time, one or more counts ofthe product stored in each fulfillment center 200, which fulfillmentcenter stores each product, expected or current orders for that product,or the like.

In some embodiments, FO system 113 may determine a PDD for each producton a periodic basis (e.g., hourly) and store it in a database forretrieval or sending to other systems (e.g., external front end system103, SAT system 101, shipment and order tracking system 111). In otherembodiments, FO system 113 may receive electronic requests from one ormore systems (e.g., external front end system 103, SAT system 101,shipment and order tracking system 111) and calculate the PDD on demand.

Fulfillment messaging gateway (FMG) 115, in some embodiments, may beimplemented as a computer system that receives a request or response inone format or protocol from one or more systems in system 100, such asFO system 113, converts it to another format or protocol, and forward itin the converted format or protocol to other systems, such as WMS 119 or3^(rd) party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system 117, in some embodiments, may beimplemented as a computer system that performs forecasting functions.For example, SCM system 117 may forecast a level of demand for aparticular product based on, for example, based on a past demand forproducts, an expected demand for a product, a network-wide past demand,a network-wide expected demand, a count products stored in eachfulfillment center 200, expected or current orders for each product, orthe like. In response to this forecasted level and the amount of eachproduct across all fulfillment centers, SCM system 117 may generate oneor more purchase orders to purchase and stock a sufficient quantity tosatisfy the forecasted demand for a particular product.

Warehouse management system (WMS) 119, in some embodiments, may beimplemented as a computer system that monitors workflow. For example,WMS 119 may receive event data from individual devices (e.g., devices107A-107C or 119A-119C) indicating discrete events. For example, WMS 119may receive event data indicating the use of one of these devices toscan a package. As discussed below with respect to fulfillment center200 and FIG. 2, during the fulfillment process, a package identifier(e.g., a barcode or RFID tag data) may be scanned or read by machines atparticular stages (e.g., automated or handheld barcode scanners, RFIDreaders, high-speed cameras, devices such as tablet 119A, mobiledevice/PDA 1196, computer 119C, or the like). WMS 119 may store eachevent indicating a scan or a read of a package identifier in acorresponding database (not pictured) along with the package identifier,a time, date, location, user identifier, or other information, and mayprovide this information to other systems (e.g., shipment and ordertracking system 111).

WMS 119, in some embodiments, may store information associating one ormore devices (e.g., devices 107A-107C or 119A-119C) with one or moreusers associated with system 100. For example, in some situations, auser (such as a part- or full-time employee) may be associated with amobile device in that the user owns the mobile device (e.g., the mobiledevice is a smartphone). In other situations, a user may be associatedwith a mobile device in that the user is temporarily in custody of themobile device (e.g., the user checked the mobile device out at the startof the day, will use it during the day, and will return it at the end ofthe day).

WMS 119, in some embodiments, may maintain a work log for each userassociated with system 100. For example, WMS 119 may store informationassociated with each employee, including any assigned processes (e.g.,unloading trucks, picking items from a pick zone, rebin wall work,packing items), a user identifier, a location (e.g., a floor or zone ina fulfillment center 200), a number of units moved through the system bythe employee (e.g., number of items picked, number of items packed), anidentifier associated with a device (e.g., devices 119A-119C), or thelike. In some embodiments, WMS 119 may receive check-in and check-outinformation from a timekeeping system, such as a timekeeping systemoperated on a device 119A-119C.

3^(rd) party fulfillment (3PL) systems 121A-121C, in some embodiments,represent computer systems associated with third-party providers oflogistics and products. For example, while some products are stored infulfillment center 200 (as discussed below with respect to FIG. 2),other products may be stored off-site, may be produced on demand, or maybe otherwise unavailable for storage in fulfillment center 200. 3PLsystems 121A-121C may be configured to receive orders from FO system 113(e.g., through FMG 115) and may provide products and/or services (e.g.,delivery or installation) to customers directly. In some embodiments,one or more of 3PL systems 121A-121C may be part of system 100, while inother embodiments, one or more of 3PL systems 121A-121C may be outsideof system 100 (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) 123, in some embodiments, maybe implemented as a computer system with a variety of functions. Forexample, in some embodiments, FC Auth 123 may act as a single-sign on(SSO) service for one or more other systems in system 100. For example,FC Auth 123 may enable a user to log in via internal front end system105, determine that the user has similar privileges to access resourcesat shipment and order tracking system 111, and enable the user to accessthose privileges without requiring a second log in process. FC Auth 123,in other embodiments, may enable users (e.g., employees) to associatethemselves with a particular task. For example, some employees may nothave an electronic device (such as devices 119A-119C) and may insteadmove from task to task, and zone to zone, within a fulfillment center200, during the course of a day. FC Auth 123 may be configured to enablethose employees to indicate what task they are performing and what zonethey are in at different times of day.

Labor management system (LMS) 125, in some embodiments, may beimplemented as a computer system that stores attendance and overtimeinformation for employees (including full-time and part-time employees).For example, LMS 125 may receive information from FC Auth 123, WMA 119,devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The particular configuration depicted in FIG. 1A is an example only. Forexample, while FIG. 1A depicts FC Auth system 123 connected to FO system113, not all embodiments require this particular configuration. Indeed,in some embodiments, the systems in system 100 may be connected to oneanother through one or more public or private networks, including theInternet, an Intranet, a WAN (Wide-Area Network), a MAN(Metropolitan-Area Network), a wireless network compliant with the IEEE802.11a/b/g/n Standards, a leased line, or the like. In someembodiments, one or more of the systems in system 100 may be implementedas one or more virtual servers implemented at a data center, serverfarm, or the like.

FIG. 2 depicts a fulfillment center 200. Fulfillment center 200 is anexample of a physical location that stores items for shipping tocustomers when ordered. Fulfillment center (FC) 200 may be divided intomultiple zones, each of which are depicted in FIG. 2. These “zones,” insome embodiments, may be thought of as virtual divisions betweendifferent stages of a process of receiving items, storing the items,retrieving the items, and shipping the items. So while the “zones” aredepicted in FIG. 2, other divisions of zones are possible, and the zonesin FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound zone 203 represents an area of FC 200 where items are receivedfrom sellers who wish to sell products using system 100 from FIG. 1A.For example, a seller may deliver items 202A and 202B using truck 201.Item 202A may represent a single item large enough to occupy its ownshipping pallet, while item 202B may represent a set of items that arestacked together on the same pallet to save space.

A worker will receive the items in inbound zone 203 and may optionallycheck the items for damage and correctness using a computer system (notpictured). For example, the worker may use a computer system to comparethe quantity of items 202A and 202B to an ordered quantity of items. Ifthe quantity does not match, that worker may refuse one or more of items202A or 202B. If the quantity does match, the worker may move thoseitems (using, e.g., a dolly, a handtruck, a forklift, or manually) tobuffer zone 205. Buffer zone 205 may be a temporary storage area foritems that are not currently needed in the picking zone, for example,because there is a high enough quantity of that item in the picking zoneto satisfy forecasted demand. In some embodiments, forklifts 206 operateto move items around buffer zone 205 and between inbound zone 203 anddrop zone 207. If there is a need for items 202A or 202B in the pickingzone (e.g., because of forecasted demand), a forklift may move items202A or 202B to drop zone 207.

Drop zone 207 may be an area of FC 200 that stores items before they aremoved to picking zone 209. A worker assigned to the picking task (a“picker”) may approach items 202A and 202B in the picking zone, scan abarcode for the picking zone, and scan barcodes associated with items202A and 202B using a mobile device (e.g., device 119B). The picker maythen take the item to picking zone 209 (e.g., by placing it on a cart orcarrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored onstorage units 210. In some embodiments, storage units 210 may compriseone or more of physical shelving, bookshelves, boxes, totes,refrigerators, freezers, cold stores, or the like. In some embodiments,picking zone 209 may be organized into multiple floors. In someembodiments, workers or machines may move items into picking zone 209 inmultiple ways, including, for example, a forklift, an elevator, aconveyor belt, a cart, a handtruck, a dolly, an automated robot ordevice, or manually. For example, a picker may place items 202A and 202Bon a handtruck or cart in drop zone 207 and walk items 202A and 202B topicking zone 209.

A picker may receive an instruction to place (or “stow”) the items inparticular spots in picking zone 209, such as a particular space on astorage unit 210. For example, a picker may scan item 202A using amobile device (e.g., device 119B). The device may indicate where thepicker should stow item 202A, for example, using a system that indicatean aisle, shelf, and location. The device may then prompt the picker toscan a barcode at that location before stowing item 202A in thatlocation. The device may send (e.g., via a wireless network) data to acomputer system such as WMS 119 in FIG. 1A indicating that item 202A hasbeen stowed at the location by the user using device 1196.

Once a user places an order, a picker may receive an instruction ondevice 1196 to retrieve one or more items 208 from storage unit 210. Thepicker may retrieve item 208, scan a barcode on item 208, and place iton transport mechanism 214. While transport mechanism 214 is representedas a slide, in some embodiments, transport mechanism may be implementedas one or more of a conveyor belt, an elevator, a cart, a forklift, ahandtruck, a dolly, a cart, or the like. Item 208 may then arrive atpacking zone 211.

Packing zone 211 may be an area of FC 200 where items are received frompicking zone 209 and packed into boxes or bags for eventual shipping tocustomers. In packing zone 211, a worker assigned to receiving items (a“rebin worker”) will receive item 208 from picking zone 209 anddetermine what order it corresponds to. For example, the rebin workermay use a device, such as computer 119C, to scan a barcode on item 208.Computer 119C may indicate visually which order item 208 is associatedwith. This may include, for example, a space or “cell” on a wall 216that corresponds to an order. Once the order is complete (e.g., becausethe cell contains all items for the order), the rebin worker mayindicate to a packing worker (or “packer”) that the order is complete.The packer may retrieve the items from the cell and place them in a boxor bag for shipping. The packer may then send the box or bag to a hubzone 213, e.g., via forklift, cart, dolly, handtruck, conveyor belt,manually, or otherwise.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags(“packages”) from packing zone 211. Workers and/or machines in hub zone213 may retrieve package 218 and determine which portion of a deliveryarea each package is intended to go to, and route the package to anappropriate camp zone 215. For example, if the delivery area has twosmaller sub-areas, packages will go to one of two camp zones 215. Insome embodiments, a worker or machine may scan a package (e.g., usingone of devices 119A-119C) to determine its eventual destination. Routingthe package to camp zone 215 may comprise, for example, determining aportion of a geographical area that the package is destined for (e.g.,based on a postal code) and determining a camp zone 215 associated withthe portion of the geographical area.

Camp zone 215, in some embodiments, may comprise one or more buildings,one or more physical spaces, or one or more areas, where packages arereceived from hub zone 213 for sorting into routes and/or sub-routes. Insome embodiments, camp zone 215 is physically separate from FC 200 whilein other embodiments camp zone 215 may form a part of FC 200.

Workers and/or machines in camp zone 215 may determine which routeand/or sub-route a package 220 should be associated with, for example,based on a comparison of the destination to an existing route and/orsub-route, a calculation of workload for each route and/or sub-route,the time of day, a shipping method, the cost to ship the package 220, aPDD associated with the items in package 220, or the like. In someembodiments, a worker or machine may scan a package (e.g., using one ofdevices 119A-119C) to determine its eventual destination. Once package220 is assigned to a particular route and/or sub-route, a worker and/ormachine may move package 220 to be shipped. In exemplary FIG. 2, campzone 215 includes a truck 222, a car 226, and delivery workers 224A and224B. In some embodiments, truck 222 may be driven by delivery worker224A, where delivery worker 224A is a full-time employee that deliverspackages for FC 200 and truck 222 is owned, leased, or operated by thesame company that owns, leases, or operates FC 200. In some embodiments,car 226 may be driven by delivery worker 224B, where delivery worker224B is a “flex” or occasional worker that is delivering on an as-neededbasis (e.g., seasonally). Car 226 may be owned, leased, or operated bydelivery worker 224B.

Referring to FIG. 3, a schematic block diagram 300 illustrating anexemplary embodiment of a system comprising a stowing error monitoringsystem 301 for stowing inbound products. Stowing error monitoring system301 may be associated with one or more systems in system 100 of FIG. 1A.For example, stowing error monitoring system 301 may be implemented aspart of the warehouse management system 119. Stowing error monitoringsystem 301, in some embodiments, may be implemented as a computer systemthat receives and stores notifications of stowing errors associated withone or more inbound products, resolves stowing errors, and modifies adatabase, such as database 304, to store information associated with thestowing errors. For example, stowing error monitoring system 301 mayinclude one or more processors 305, which may receive a notification ofa stowing error associated with a tote identifier of a tote containingan inbound product. One or more processors 305 may be configured tomodify a database, such as database 304, to assign the stowing error tothe tote identifier. By way of example, database 304 may store aninventory of every inbound product with a stowing error. Database 304may further store other information associated with each inboundproduct, including but not limited to product identifier associated witheach product, inbound quantity of each product, location identifierassociated with each product, stowing error associated with eachproduct, physical quantity and expected quantity of each product, anddetails associated with the stowing error. Database 304 may include oneor more memory devices that store information and are accessed throughnetwork 302. By way of example, database 304 may include Oracle™databases, Sybase™ databases, or other relational databases ornon-relational databases, such as Hadoop sequence files, HBase, orCassandra. While database 304 is illustrated as being included in thesystem 300, it may alternatively be located remotely from system 300. Inother embodiments, database 304 may be incorporated into stowing errormonitoring system 301, server 303, and/or user device 306. Database 304may include computing components (e.g., database management system,database server, etc.) configured to receive and process requests fordata stored in memory devices of database 304 and to provide data fromdatabase 304.

In some embodiments, one or more processors 305 may receive anotification of a stowing error associated with a tote identifier of atote containing an inbound product from a server 303, via network 302.After receiving the notification of the stowing error, one or moreprocessors 305 may modify database 304 to assign the stowing error tothe associated tote identifier. As such, when the tote identifierassociated with a tote containing the inbound product is scanned, forexample by a remote device (not shown) in stowing error monitoringsystem 301, one or more processors 305 may send the stowing error, andits related information, for display to user device 306.

System 300 may also comprise a network 302 and a server 303. Stowingerror monitoring system 301, server 303, user device 306, and database304 may be connected and be able to communicate with each other vianetwork 302. Network 302 may be one or more of a wireless network, awired network or any combination of wireless network and wired network.For example, network 302 may include one or more of a fiber opticnetwork, a passive optical network, a cable network, an Internetnetwork, a satellite network, a wireless LAN, a Global System for MobileCommunication (“GSM”), a Personal Communication Service (“PCS”), aPersonal Area Network (“PAN”), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE802.11b, 802.15.1, 802.11n and 802.11g or any other wired or wirelessnetwork for transmitting and receiving data.

In addition, network 302 may include, but not be limited to, telephonelines, fiber optics, IEEE Ethernet 802.3, a wide area network (“WAN”), alocal area network (“LAN”), or a global network such as the Internet.Also network 302 may support an Internet network, a wirelesscommunication network, a cellular network, or the like, or anycombination thereof. Network 302 may further include one network, or anynumber of the exemplary types of networks mentioned above, operating asa stand-alone network or in cooperation with each other. Network 302 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 302 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 302 is depicted as a single network, it should be appreciatedthat according to one or more embodiments, network 302 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Server 303 may be a web server. Server 303, for example, may includehardware (e.g., one or more computers, including processors, storage,and input/output devices) and/or software (e.g., one or moreapplications) that deliver web content that can be accessed by, forexample a user through a network (e.g., network 302), such as theInternet. Server 303 may use, for example, a hypertext transfer protocol(HTTP or sHTTP) to communicate with a user. The web pages delivered tothe user may include, for example, HTML documents, which may includeimages, style sheets, and scripts in addition to text content.

In some embodiments, server 303 may comprise one or more processors 307configured to receive a notification of a stowing error associated withan inbound product from user device 306, via network 302. Once one ormore processors 307 receives the notification of the stowing error, oneor more processors 307 may modify database 304 to assign the stowingerror to a tote identifier associated with a tote containing the inboundproduct. One or more processors 307 may also be configured toautomatically report the stowing error to the stowing error monitoringsystem 301. Additionally or alternatively, one or more processors 307may automatically report the notification of the stowing error uponreceiving the notification of the stowing error from user device 306,and the stowing error monitoring system 301 may be configured to modifydatabase 304 to assign the stowing error to the tote identifier.

A user program such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP and server 303 may respondwith the content of that resource or an error message if unable to doso. Server 303 also may enable or facilitate receiving content from theuser so the user may be able to, for example, submit web forms,including uploading of files. Server 303 may also support server-sidescripting using, for example, Active Server Pages (ASP), PHP, or otherscripting languages. Accordingly, the behavior of server 303 can bescripted in separate files, while the actual server software remainsunchanged.

In other embodiments, server 303 may be an application server, which mayinclude hardware and/or software that is dedicated to the efficientexecution of procedures (e.g., programs, routines, scripts) forsupporting its applied applications. Server 303 may comprise one or moreapplication server frameworks, including, for example, Java applicationservers (e.g., Java platform, Enterprise Edition (Java EE), the .NETframework from Microsoft®, PHP application servers, and the like). Thevarious application server frameworks may contain a comprehensiveservice layer model. Server 303 may act as a set of componentsaccessible to, for example, an entity implementing system 100, throughan API defined by the platform itself. For Web applications, thesecomponents may be performed in, for example, the same runningenvironment as web servers, and application servers may support theconstruction of dynamic pages. Application servers also may implementservices, such as, for example, clustering, fail-over, andload-balancing. In various embodiments, where application servers areJava application servers, the web servers may behave like an extendedvirtual machine for running applications, transparently handlingconnections to databases associated with a backend on one side, and,connections to the Web client on the other.

User device 306 may be any computer device, or communications deviceincluding, but not limited to, a server, a network appliance, a personalcomputer (PC), a workstation, a mobile device, a phone, a handheld PC, apersonal digital assistant (PDA), a thin client, a tablet computer, asmartphone, a fat client, an Internet browser, or other device. Userdevice 306 may also be a tablet computer. Non-limiting examples of atablet computer include an iPad, Kindle Fire, Playbook, Touchpad, andthe like. User device 306 may be associated with a user having one ormore accounts. For example, a user may download an application, such asa stowing app 400 in FIGS. 4A-4C, to user device 306. As discussed inmore detail below, stowing app 400 may provide a graphical userinterface (GUI) to access services provided by one or more processors307 of server 303 and/or one or more processors 305 of stowing errormonitoring system 301. The services, for example, may include an accountprofile. User device 306 may be configured to access the account profileassociated with the user. When the user first launches stowing app 400on user device 306, stowing app 400 may prompt the user to either createan account profile or log-in to an account profile. User device 306 maycomprise one or more processors 308 that may be configured to create anaccount profile in response to input from the user and store the accountof the user in database 304, via network 302. Additionally oralternatively, one or more processors 308 may be configured to log-in toan account profile of the user in response to input from the user, e.g.,in response to receiving username and password from the user. Once oneor more processors 308 successfully logs in to the account profile ofthe user, one or more processors 308 may grant access to the accountprofile to the user of user device 306. For example, one or moreprocessors 308 may display stowing app 400 on the user device 306.

FIGS. 4A-4C depict exemplary embodiments of graphical user interfaces(GUIs) 410 that may be presented to the user on user device 306 viastowing app 400. In particular, FIG. 4A shows an example embodiment ofan interface 410 on user device 306 configured to display one or moreinputs from the user. For example, interface 410 of the stowing app 400may be configured to receive a tote identifier 401, a product identifier403, a location identifier 404, and/or an inbound quantity 405associated with an inbound product. One or more processors 308 of userdevice 306 may be configured to receive a tote identifier 401 and sendthe tote identifier 401 to server 303 via network 302. For example, auser may scan a tote identifier using user device 306, and one or moreprocessors 308 may automatically display the scanned tote identifier 401on the interface 410.

Based on the tote identifier 401, one or more processors 307 of server303 may predict a location for stowing at least one product contained inthe tote. A location may be a location within FC 200 for stowing the atleast one product contained in the tote. By way of example, one or moreprocessors 307 may determine a location of user device 306 and determineone or more empty locations within FC 200 that are capable of receivingand stowing the at least one product. Among the one or more emptylocations within FC 200 determined, one or more processors 307 mayselect an empty location closest to the location of user device 306 asthe location for stowing the at least one product. Additionally oralternatively, one or more processors 307 may predict a location forstowing the at least one product based on one or more restrictionswithin FC 200. For example, each location for stowing products in FC 200may be different in size. As such, one or more processors 307 may selecta location, among the empty locations within FC 200, that is bothclosest to the location of user device 306 and has a size limit that iscapable of stowing the at least one product. In some embodiments, everyproduct that needs to be maintained at a particular temperature (e.g.,refrigerated or frozen) may need to be placed at a particular locationwithin FC 200. Therefore, one or more processors 307 may select alocation, among the empty locations within FC 200, that is closest tothe location of user device 306 and is capable of maintaining apredetermined temperature of the at least one product. One or moreprocessors 307 may provide the location recommendation to one or moreprocessors 308 of user device 306 such that one or more processors 308may display location recommendation 402 on the interface 410. As sch,one or more processors 308 may be configured to display locationrecommendation 402 for stowing the at least one product on interface 410upon receiving the tote identifier 401.

Referring now to FIG. 4B, once the at least one product is stowed withinFC 200, the user may input a product identifier 403, location identifier404, and/or inbound quantity 405 of the at least one product usinginterface 410. Product identifier 403 may include a combination ofnumbers, letters, and/or special characters to identify a product. Forexample, product identifier 403 may include a stock keeping unit (SKU)associated with the product. Location identifier 404 may include acombination of numbers, letters, and/or special characters to identify aposition at which a product is to be stowed. For example, each locationwithin FC 200 for stowing an inbound product may be assigned anidentifier, such as location identifier 404. One or more processors 308may be configured to receive and transmit product identifier 403,location identifier 404, and/or inbound quantity 405 of the at least oneproduct to one or more processors 307 of server 303. One or moreprocessors 307 may be configured to modify database 304 to assignlocation identifier 404 and inbound quantity 405 to product identifier403. Additionally or alternatively, one or more processors 308 of userdevice 306 may be configured to modify database 304 to assign locationidentifier 404 and inbound quantity 405 to product identifier 403.

After inputting information associated with the at least one product tobe stowed, the user may stow the at least one product by touching thestow button 406. Once the user touches the stow button 406, one or moreprocessors 308 may be configured to determine that the at least oneproduct is ready for stowing and stow the at least one product. As seenin FIG. 4C, upon stowing the at least one product, one or moreprocessors 308 may display a notification 408 on interface 410indicating that stowing is complete. One or more processors 308 may alsosend a notification to server 303 and/or stowing error monitoring system301 indicating that stowing of the at least one product is complete. Insome embodiments, one or more processors 308 of user device 306 and/orone or more processors 307 of server 303 may be configured to modifydatabase 304 to assign a status to the product identifier 403 indicatingthat stowing is complete. In some embodiments, the user may return tointerface 410 in FIG. 4A to continue stowing remaining inbound productsin remaining totes. If the user has finished stowing inbound products,the user may touch button 407 to finish stowing. Once the user touchesbutton 407, one or more processors 308 may cause the stowing app 400 toexit from interface 410. In other embodiments, as will be discussed inreference to FIGS. 5A-5C, once the user touches button 407, one or moreprocessors 308 may display an interface, such as interface 510 of FIGS.5A-5C, configured to allow the user to input any stowing error.

FIGS. 5A-5C depict exemplary embodiments of GUIs 510 that may bepresented to the user on user device 306 via stowing app 500. Stowingapp 500 may be the same as stowing app 400 in FIGS. 4A-4C. Inparticular, FIG. 5A shows an example embodiment of an interface 510 onuser device 306 configured to display one or more inputs from the user.For example, interface 510 of the stowing app 500 may be configured toreceive a tote identifier 501, a product identifier 503, a locationidentifier 504, and/or an inbound quantity 505 associated with aninbound product. One or more processors 308 of user device 306 may beconfigured to receive a tote identifier 501 and send the tote identifier501 to server 303 via network 302. For example, a user may scan a toteidentifier 501 using user device 306, and one or more processors 308 mayautomatically display the scanned tote identifier 501 on the interface510.

Based on the tote identifier 501, one or more processors 307 of server303 may predict a location for stowing at least one product contained inthe tote. A location may be a location within FC 200 for stowing the atleast one product contained in the tote. By way of example, one or moreprocessors 307 may determine a location of user device 306 and determineone or more empty locations within FC 200 that are capable of receivingand stowing the at least one product. Among the one or more determinedempty locations within FC 200, one or more processors 307 may select anempty location closest to the location of user device 306 as thelocation for stowing the at least one product. One or more processors307 may provide the location recommendation to one or more processors308 of user device 306 such that one or more processors 308 may displaylocation recommendation 502 on the interface 510. As sch, one or moreprocessors 308 may be configured to display location recommendation 502for stowing the at least one product on interface 510 upon receiving thetote identifier 501.

As discussed above with reference to FIG. 4B, the user may also inputproduct identifier 503, location identifier 504, and/or inbound quantity505 associated with at least one product contained in the tote in orderto complete stowing the at least one product within FC 200. Once theuser has finished stowing, the user may touch button 507 in order tofinish stowing. Before finishing stowing, one or more processors 308 ofuser device 306 may display a prompt to the user such that the user mayreport any stowing error, if necessary.

By way of example, referring to FIG. 5B, when the user touches button507 to finish stowing, one or more processors 308 may display a prompt508 to the user via interface 510, requesting that the user confirmwhether the tote is empty. If the tote is empty, the user may press“Yes” in prompt 508. If the tote is not empty and the user has finishedstowing the products, the user may press “No,” indicating that there isat least one remaining product in the tote with a stowing error. Forexample, there may be at least one remaining product in the tote thatcannot be stowed for a particular reason.

As seen in FIG. 5C, if the user presses “No” in prompt 508, one or moreprocessors 308 may display another prompt 509 requesting that the userselect a cause for the stowing error. A cause for the stowing error mayinclude, but is not limited to, product damage, barcode damage, orincorrect product. For example, if an inbound product is damaged andcannot be stowed for purchase by a customer, the user may select“Product Damage” button in prompt 509. If an inbound product has adamaged barcode that cannot be scanned properly, the user may select“Barcode Damage” button in prompt 509. If an inbound product is missingfrom the inventory and should not be stowed for purchase by a customer,the user may select “Incorrect Product” button in prompt 509. Once theuser selects a cause for the stowing error in prompt 509, the user maypress “Submit Stowing Error” button in prompt 509, after which one ormore processors 308 may cause the stowing app 500 to exit from interface510.

In some embodiments, one or more processors 308 may modify database 304to assign the stowing error and/or the cause of the stowing error to thetote identifier. In other embodiments, one or more processors 308 maytransmit the stowing error and/or the cause of the stowing error to oneor more processors 307 of server 303 and/or one or more processors 305of stowing error monitoring system 301. Then, one or more processors 307of server 303 and/or one or more processors 305 of stowing errormonitoring system 301 may modify database 304 to assign the stowingerror and/or the cause of the stowing error to the tote identifier. Assuch, when stowing error monitoring system 301 receives a notificationof a stowing error, the cause of the stowing error stored in database304 can be determined by looking up or scanning the tote identifier.

FIG. 6 shows information associated with the inbound products that maybe stored in a table of exemplary database 304. As discussed above, oneor more processors 308 or user device 306, one or more processors 307 ofserver 303, and/or one or more processors 305 of stowing errormonitoring system 301 may be configured to modify database 304 to storeinformation associated with inbound products. By way of example, whentotes containing inbound products arrive at FC 200 for stowing, one ormore processors 307 of server 303 may receive tote identifiers, such astote identifiers 401 or 501 associated with the totes containing theinbound products for stowing. One or more processors 307 may receivetote identifiers, from user device 306, when a user scans the toteidentifiers, using user device 306, and store the tote identifiers indatabase 304. One or more processors 307 may also store a timestamp,representing a time at which each tote identifier is received from userdevice 306. As such, database 304 may maintain an updated record of thetime, at which each tote containing inbound products are received at FC200. In some embodiments, one or more processors 307 may be configuredto store an inventory of every inbound product contained in each tote.For example, when one or more processors 307 receives a productidentifier, such as product identifier 403 or 503, associated with atleast one inbound product, one or more processors 307 may be configuredto assign the product identifier to a tote identifier associated with atote containing the product in database 304. The product identifier mayinclude, for example, a stock keeping unit (SKU) associated with theproduct. One or more processors 307 may also be configured to store aninbound quantity, such as inbound quantity 405 or 505, of each inboundproduct in database 304. For example, one or more processors 307 maydetermine an inbound quantity of a product contained in a tote. One ormore processors 307, then, may modify database 304 to assign the inboundquantity to the product identifier associated with the product and thetote identifier associated with the tote containing the product.

In some embodiments, one or more processors 307 may be configured tostore a stowing error associated with an inbound product in database304. For example, when one or more processors 307 receives anotification of a stowing error from user device 306, one or moreprocessors 307 may modify database 304 to assign the stowing error to atote identifier associated with a tote containing the inbound productwith the stowing error. As such, when the product identifier associatedwith the inbound product is scanned or looked up in database 304, one ormore processors 307 may be configured to send a cause of the stowingerror for display to a remote device. For example, one or moreprocessors 307 may be configured to send a cause of the stowing errorfor display to user device 306 and/or stowing error monitoring system301.

In some embodiments, the stowing error may comprise an overage or ashortage. For example, when a physical quantity of an inbound product isless than an expected quantity of the inbound product, the stowing errormay comprise a shortage. In some embodiments, when a physical quantityof an inbound product is greater than an expected quantity of theinbound product, the stowing error may comprise an overage. An expectedquantity of the inbound product, for example, may be a virtual inventoryof the inbound product. In some embodiments, an expected quantity of theinbound product and/or a virtual inventory of the inbound product may bea quantity or an inventory of an inbound product that a customer is ableto see on a user interface as being available for purchase. In someembodiments, one or more processors 307 may store a physical quantity ofan inbound product and an expected quantity of an inbound product indatabase 304. The physical quantity of the inbound product may comprise,for example, a quantity of the inbound product that is stowed in FC 200.The expected quantity of the inbound product may comprise, for example,a quantity of the inbound product that is expected to be available forpurchase by a customer. In some embodiments, when the stowing errorcomprises shortage, one or more processors 307 may be configured torequest, via user device 306, a difference between the physical quantityof the inbound product and the expected quantity of the inbound product,and store the difference in database 304.

In some embodiments, when the stowing error comprises overage, one ormore processors 307 may determine a cause for the overage and modifydatabase 304 to store the cause for the overage. As discussed above, acause for the overage may include, but is not limited to, productdamage, barcode damage, or incorrect product. By way of example, whenthe stowing error comprises overage and the cause for overage comprisesat least one of product damage or barcode damage, one or more processors307 may be configured to provide, via user device 306, a locationrecommendation for transferring the product with at least one of theproduct damage or the barcode damage. The product with at least one ofthe product damage or the barcode damage may be transferred such thatthe stowing error can be resolved. One or more processors 307 may alsorequest, via user device 306, a quantity of a product with a stowingerror, such as a quantity of a product with product damage, a quantityof a product with barcode damage, or a quantity of incorrect products.One or more processors 307 may modify database 304 to store the quantityof products with stowing errors in each tote in database 304.

In some embodiments, database 304 may be configured to store stowingerror status. By way of example, when one or more processors 307receives a notification of a stowing error from user device 306, one ormore processors 307 may send the notification of the stowing error toone or more processors 305 of stowing error monitoring system 301. Oneor more processors 305 may determine whether the stowing error has beenresolved and modify database 304 to assign a stowing error status toeach stowing error. Stowing error status may include, but not limitedto, resolved, reported, tote modified, or the like. For example, if acause for the stowing error comprises a barcode damage and if thebarcode has been fixed, one or more processors 305 may modify database304 to change the stowing error status to indicate that the stowingerror has been resolved. In some embodiments, the stowing error statusmay indicate that the stowing error has been reported, if one or moreprocessors 305 receives a notification of the stowing error but thestowing error has not been resolved yet. In other embodiments, thestowing error status may indicate that the tote has been modified, ifone or more processors 305 determines that a cause for the stowing errorcomprises a barcode damage, and the barcode of a product within a totehas been fixed. Other status identifiers are possible as well.

By modifying database 304 to assign a stowing error to a tote identifierassociated with a tote containing inbound products, one or moreprocessors 307 may be configured to determine various informationassociated with the stowing error, as well as various informationassociated with the inbound product with the stowing error, by scanningor looking up the tote identifier. Such information stored in database304 may be provided for display on remote devices, such as user device306 and/or stowing error monitoring system 301. While various elementsof server 303, such as one or more processors 307, are referenced inexplaining database 304 of FIG. 6, it should be noted that variouselements of stowing error monitoring system 301, such as one or moreprocessors 305, and/or various elements of user device 306, such as oneor more processors 308, may be configured to modify and storeinformation in database 304.

FIG. 7 is a flow chart illustrating an exemplary method 700 for stowingproducts. This exemplary method is provided by way of example. Method700 shown in FIG. 7 can be executed or otherwise performed by one ormore combinations of various systems. Method 700 as described below maybe carried out by stowing error monitoring system 301, server 303,and/or user device 306, as shown in FIG. 3, by way of example. Whilevarious elements of server 303 are referenced in explaining the methodof FIG. 7, it should be noted that various elements of stowing errormonitoring system 301 and/or user device 306 may carry out the method ofFIG. 7. Each block shown in FIG. 7 represents one or more processes,methods, or subroutines in the exemplary method 700. Referring to FIG.7, exemplary method 700 may begin at block 701.

At block 701, one or more processors 307 may receive, from user device306, a tote identifier associated with a tote containing at least oneinbound product for stowing. As discussed above, the tote identifier,such as tote identifier 401 or 501, may comprise a combination ofletters, numbers, and/or special characters and may be unique to eachtote, such that the tote identifier may identify a particular tote. Atblock 702, based on the tote identifier received, one or more processors307 may predict a location for stowing the at least one productcontained in the tote. By way of example, one or more processors 307 maydetermine a location of user device 306, from which the tote identifierwas received. Then, one or more processors 307 may determine emptylocations within FC 200 that is capable of receiving the at least oneproduct for stowing. For example, one or more processors 307 mayidentify every empty location within FC 200 that is capable of stowingthe at least one product. Among the determined empty locations within FC200, one or more processors 307 may select an empty location that isclosest to the location of user device 306 as the location for stowingthe at least one product.

Then, method 700 may proceed to block 703, at which one or moreprocessors 307 may provide a location recommendation (e.g., locationrecommendation 402 or 502) for stowing the at least one product based onthe predicted location at block 702. As such, one or more processors 307may provide a location recommendation for stowing the at least oneproduct that is closest in distance to the user of user device 306within FC 200. While it may not be required for the user of user device306 to follow the location recommendation, by providing a locationrecommendation, time spent to find an empty location within FC 200 forstowing the at least one product can be reduced. In addition, whileconventional systems and methods for stowing products designate fixedlocations within a fulfillment center for stowing each product, one ormore processors 307 may reduce stowing time, shipment time, and,ultimately, delivery time by providing a location recommendation that isclosest to the user of user device 306.

Once a location recommendation has been provided, method 700 may proceedto block 704. At block 704, one or more processors 307 may receive aproduct identifier (e.g., product identifier 403 or 503), a locationidentifier (e.g., location identifier 404 or 504), and an inboundquantity (e.g., inbound quantity 405 or 505) of the at least one productto be stowed. By way of example, after the user of user device 306inputs a product identifier (e.g., product identifier 403 or 503), alocation identifier (e.g., location identifier 404 or 504), and aninbound quantity (e.g., inbound quantity 405 or 505) of the at least oneproduct in stowing app 400 or 500, one or more processors 308 may sendthe product identifier, location identifier, and inbound quantity to oneor more processors 307 of server 303.

At block 705, one or more processors 307 of server 303 may modifydatabase 304 to assign the product identifier 403 or 503 to the toteidentifier 401 or 501. In addition, one or more processors 307 maymodify database 304 to assign the location identifier 404 or 504 and theinbound quantity 405 or 505 to the product identifier 403 or 503. Assuch, when the tote identifier 401 or 501 is scanned or looked up indatabase 304, various information associated with products contained inthe tote associated with the tote identifier 401 or 501 may bedetermined. For example, as seen in FIG. 6, by scanning the toteidentifier 401 or 501, a user may determine products contained in thetote, inbound quantity of the products, stowing errors associated withthe products, physical and expected quantity of the products, stowingerror status, incorrect product quantity, and/or damage quantity. Byscanning the tote identifier 401 or 501, a user may determine whetherthere is a stowing error associated with products contained in aparticular tote and also determine a cause of the stowing error, basedon information stored in database 304.

Once database 304 has been modified to assign the location identifierand the inbound quantity to the product identifier, method 700 mayproceed to block 706. At block 706, one or more processors 307 may beconfigured to receive a notification of a stowing error associated withthe tote identifier. For example, as discussed with respect to FIG. 5,the user of user device 306 may report a stowing error in stowing app500. Then, one or more processors 308 of user device 306 may send anotification of a stowing error to one or more processors 307 of server303 and/or one or more processors 305 of stowing error monitoring system301. Additionally or alternatively, one or more processors 307 of server303 may receive a notification of a stowing error from user device 306and send the notification of the stowing error to one or more processors305 of stowing error monitoring system 301.

As discussed above, the stowing error may comprise an overage or ashortage. For example, when a physical quantity of an inbound product isless than an expected quantity of the inbound product, the stowing errormay comprise a shortage. In some embodiments, when a physical quantityof an inbound product is greater than an expected quantity of theinbound product, the stowing error may comprise an overage.

After receiving the notification of the stowing error, method 700 mayproceed to block 707, at which one or more processors 307 may modifydatabase 304 to assign the stowing error to the tote identifier, such astote identifier 401 or 501. For example, if there is a stowing errorassociated with a particular product contained in a particular tote, oneor more processors 307 may modify database 304 to assign the stowingerror to a tote identifier associated with the particular totecontaining the particular product. As such, when a user scans or looksup the tote identifier associated with the particular tote, the user candetermine whether there is a stowing error associated with productscontained in the particular tote and also determine a cause of thestowing error, based on information stored in database 304.

Method 700 may proceed to block 708, at which one or more processors 307may automatically report the stowing error. By way of example, one ormore processors 307 of server 303 may receive a notification of astowing error from user device 306 and automatically send thenotification of the stowing error to one or more processors 305 ofstowing error monitoring system 301. As such, stowing error monitoringsystem 301 may be configured to monitor a real-time or near real-timestatus of all stowing errors that arise within FC 200. Accordingly,stowing errors may be resolved more quickly and efficiently, and thus,stowing time, shipment time, and delivery time may be reduced.

FIG. 8 is a flow chart illustrating an exemplary method 800 for stowingproducts. This exemplary method is provided by way of example. Method800 shown in FIG. 8 can be executed or otherwise performed by one ormore combinations of various systems. Method 800 as described below maybe carried out by stowing error monitoring system 301, server 303,and/or user device 306, as shown in FIG. 3, by way of example. Whilevarious elements of server 303 are referenced in explaining the methodof FIG. 8, it should be noted that various elements of stowing errormonitoring system 301 and/or user device 306 may carry out the method ofFIG. 8. Each block shown in FIG. 8 represents one or more processes,methods, or subroutines in the exemplary method 800. Referring to FIG.8, exemplary method 800 may begin at block 801.

At block 801, one or more processors 307 may receive, from user device306, a tote identifier associated with a tote containing at least oneinbound product for stowing. As discussed above, the tote identifier,such as tote identifier 401 or 501, may comprise a combination ofletters, numbers, and/or special characters and may be unique to eachtote, such that the tote identifier may identify a particular tote. Atblock 802, based on the tote identifier received, one or more processors307 may predict a location for stowing the at least one productcontained in the tote. By way of example, one or more processors 307 maydetermine a location of user device 306, from which the tote identifierwas received. Then, one or more processors 307 may determine emptylocations within FC 200 that is capable of receiving the at least oneproduct for stowing. For example, one or more processors 307 mayidentify every empty location within FC 200 that is capable of stowingthe at least one product. Among the determined empty locations within FC200, one or more processors 307 may select an empty location that isclosest to the location of user device 306 as the location for stowingthe at least one product. Then, method 800 may proceed to block 803, atwhich one or more processors 307 may provide a location recommendation(e.g., location recommendation 402 or 502) for stowing the at least oneproduct based on the predicted location at block 802. As such, one ormore processors 307 may provide a location recommendation for stowingthe at least one product that is closest in distance to the user of userdevice 306 within FC 200. While it may not be required for the user ofuser device 306 to follow the location recommendation, by providing alocation recommendation, time spent to find an empty location within FC200 for stowing the at least one product can be reduced. In addition,while conventional systems and methods for stowing products designatefixed locations within a fulfillment center for stowing each product,one or more processors 307 may reduce stowing time, shipment time, and,ultimately, delivery time by providing a location recommendation that isclosest to the user of user device 306.

Once a location recommendation has been provided, method 800 may proceedto block 804. At block 804, one or more processors 307 may receive aproduct identifier (e.g., product identifier 403 or 503), a locationidentifier (e.g., location identifier 404 or 504), and an inboundquantity (e.g., inbound quantity 405 or 505) of the at least one productto be stowed. By way of example, after the user of user device 306inputs a product identifier (e.g., product identifier 403 or 503), alocation identifier (e.g., location identifier 404 or 504), and aninbound quantity (e.g., inbound quantity 405 or 505) of the at least oneproduct in stowing app 400 or 500, one or more processors 308 may sendthe product identifier, location identifier, and inbound quantity to oneor more processors 307 of server 303.

At block 805, one or more processors 307 of server 303 may modifydatabase 304 to assign the product identifier 403 or 503 to the toteidentifier 401 or 501. In addition, one or more processors 307 maymodify database 304 to assign the location identifier 404 or 504 and theinbound quantity 405 or 505 to the product identifier 403 or 503. Assuch, when the tote identifier 401 or 501 is scanned or looked up indatabase 304, various information associated with products contained inthe tote associated with the tote identifier 401 or 501 may bedetermined. For example, as seen in FIG. 6, by scanning the toteidentifier 401 or 501, a user may determine products contained in thetote, inbound quantity of the products, stowing errors associated withthe products, physical and expected quantity of the products, stowingerror status, incorrect product quantity, and/or damage quantity. Byscanning the tote identifier 401 or 501, a user may determine whetherthere is a stowing error associated with products contained in aparticular tote and also determine a cause of the stowing error, basedon information stored in database 304.

Once database 304 has been modified to assign the location identifierand the inbound quantity to the product identifier, method 800 mayproceed to block 806. At block 806, one or more processors 307 may beconfigured to receive a notification of a stowing error associated withthe tote identifier. For example, as discussed with respect to FIG. 5,the user of user device 306 may report a stowing error in stowing app500. Then, one or more processors 308 of user device 306 may send anotification of a stowing error to one or more processors 307 of server303 and/or one or more processors 305 of stowing error monitoring system301. Additionally or alternatively, one or more processors 307 of server303 may receive a notification of a stowing error from user device 306and send the notification of the stowing error to one or more processors305 of stowing error monitoring system 301.

After receiving the notification of the stowing error, method 800 mayproceed to block 807. At block 807, one or more processors 307 maydetermine whether the stowing error comprises an overage or a shortage.As discussed above, the stowing error may comprise an overage or ashortage. For example, when a physical quantity of an inbound product isless than an expected quantity of the inbound product, the stowing errormay comprise a shortage. In some embodiments, when a physical quantityof an inbound product is greater than an expected quantity of theinbound product, the stowing error may comprise an overage.

At block 807, if one or more processors 307 determine that the stowingerror comprises an overage, method 800 may proceed to block 808. Atblock 808, when the stowing error comprises an overage, one or moreprocessors 307 may determine a cause for the overage and modify database304 to store the cause for the overage. As discussed above, a cause forthe overage may include, but is not limited to, product damage, barcodedamage, or incorrect product. As discussed above with respect to FIG.5C, the user may report a stowing error and a cause of the stowing errorusing stowing app 500. Then, one or more processors 308 of user device306 may send a cause of the stowing error to one or more processors 307of server 303.

After determining the cause for the overage, method 800 may proceed toblock 809. At block 809, one or more processors may provide, via userdevice 306, a location recommendation for transferring the totecontaining the at least one product with the stowing error such that thestowing error can be resolved. In some embodiments, the location fortransferring the tote may be based on the stowing error and the causefor the stowing error. For example, if the stowing error comprises anoverage, one or more processors 307 may recommend a first location fortransferring the tote. If the stowing error comprises a shortage, one ormore processors 307 may recommend a second location for transferring thetote. Additionally or alternatively, depending on the cause for thestowing error, one or more processors 307 may recommend a differentlocation for transferring the tote such that the stowing error may beresolved.

After providing a location recommendation for transferring the tote,method 800 may proceed to block 813, at which one or more processors 307may modify database 304 to assign the stowing error and/or the cause ofthe stowing error to a corresponding tote identifier. For example, ifthere is a stowing error associated with a particular product containedin a particular tote, one or more processors 307 may modify database 304to assign the stowing error to a tote identifier associated with theparticular tote containing the particular product. As such, when a userscans or looks up the tote identifier associated with the particulartote, the user can determine whether there is a stowing error associatedwith products contained in the particular tote and also determine acause of the stowing error, based on information stored in database 304.

Method 800 may proceed to block 814, at which one or more processors 307may automatically report the stowing error. By way of example, one ormore processors 307 of server 303 may receive a notification of astowing error from user device 306 and automatically send thenotification of the stowing error to one or more processors 305 ofstowing error monitoring system 301. As such, stowing error monitoringsystem 301 may be configured to monitor a real-time or near real-timestatus of all stowing errors that arise within FC 200. Accordingly,stowing errors may be resolved more quickly and efficiently, and thus,stowing time, shipment time, and delivery time may be reduced.

Referring back to block 807, if one or more processors 307 determinethat the stowing error does not comprise an overage, method 800 mayproceed to block 810. At block 810, one or more processors 307 maydetermine whether the stowing error comprises a shortage, e.g., when aphysical quantity of an inbound product is less than an expectedquantity of the inbound product. At block 810, if one or more processors307 determine that the stowing error does not comprise a shortage,method 800 may proceed to blocks 813 and 814. As discussed above, atblock 813, one or more processors 307 may modify database 304 to assignthe stowing error and/or the cause of the stowing error to acorresponding tote identifier. For example, if there is a stowing errorassociated with a particular product contained in a particular tote, oneor more processors 307 may modify database 304 to assign the stowingerror to a tote identifier associated with the particular totecontaining the particular product. As such, when a user scans or looksup the tote identifier associated with the particular tote, the user candetermine whether there is a stowing error associated with productscontained in the particular tote and also determine a cause of thestowing error, based on information stored in database 304. At block814, one or more processors 307 may automatically report the stowingerror. For example, one or more processors 307 of server 303 may receivea notification of a stowing error from user device 306 and automaticallysend the notification of the stowing error to one or more processors 305of stowing error monitoring system 301. As such, stowing errormonitoring system 301 may be configured to monitor a real-time or nearreal-time status of all stowing errors that arise within FC 200.Accordingly, stowing errors may be resolved more quickly andefficiently, and thus, stowing time, shipment time, and delivery timemay be reduced.

At block 810, if one or more processors 307 determine that the stowingerror comprises a shortage, method 800 may proceed to block 811. Atblock 811, one or more processors 307 may request, via user device 306,a difference between a physical quantity and an expected quantity of theat least one product with a stowing error. By way of example, one ormore processors 307 may send a request for one or more processors 308 ofuser device 306 and cause user device 306 to display a prompt oninterface 410 or 510. The prompt may request a user of user device 306to input a physical quantity of the at least one product with thestowing error and/or an expected quantity of the at least one productwith the stowing error. The physical quantity of the inbound product maycomprise, for example, a quantity of the inbound product that is stowedin FC 200. The expected quantity of the inbound product may comprise,for example, a quantity of the inbound product that is expected to beavailable for purchase by a customer. After receiving the input(s) fromthe user, one or more processors 308 may calculate a difference in thephysical quantity and the expected quantity and send the difference invalue to one or more processors 307. Additionally or alternatively, oneor more processors 308 may send the physical quantity and the expectedquantity of the at least one product with the stowing error to one ormore processors 307. One or more processors 307 may calculate thedifference in the physical quantity and the expected quantity.

After determining a difference between the physical and expectedquantities of the at least one product with the stowing error, method800 may proceed to block 812. At block 812, one or more processors 307may store the difference between the physical quantity of the productand the expected quantity of the product in database 304. For example,one or more processors 307 may modify database 304 to assign thephysical quantity, the expected quantity, and/or the difference betweenthe physical quantity and the expected quantity to the productidentifier associated with the product with the stowing error. As such,when a user scans or looks up the tote identifier in database 304, theuser can determine a quantity of each product associated with a productidentifier that exceeds an expected quantity of each product.

After receiving the notification of the stowing error, method 800 mayproceed to block 813, at which one or more processors 307 may modifydatabase 304 to assign the stowing error to the tote identifier, such astote identifier 401 or 501. For example, if there is a stowing errorassociated with a particular product contained in a particular tote, oneor more processors 307 may modify database 304 to assign the stowingerror to a tote identifier associated with the particular totecontaining the particular product. As such, when a user scans or looksup the tote identifier associated with the particular tote, the user candetermine whether there is a stowing error associated with productscontained in the particular tote and also determine a cause of thestowing error, based on information stored in database 304.

Method 800 may proceed to block 814, at which one or more processors 307may automatically report the stowing error. By way of example, one ormore processors 307 of server 303 may receive a notification of astowing error from user device 306 and automatically send thenotification of the stowing error to one or more processors 305 ofstowing error monitoring system 301. As such, stowing error monitoringsystem 301 may be configured to monitor a real-time or near real-timestatus of all stowing errors that arise within FC 200. Accordingly,stowing errors may be resolved more quickly and efficiently, and thus,stowing time, shipment time, and delivery time may be reduced.

While the present disclosure has been shown and described with referenceto particular embodiments thereof, it will be understood that thepresent disclosure can be practiced, without modification, in otherenvironments. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. Additionally,although aspects of the disclosed embodiments are described as beingstored in memory, one skilled in the art will appreciate that theseaspects can also be stored on other types of computer readable media,such as secondary storage devices, for example, hard disks or CD ROM, orother forms of RAM or ROM, USB media, DVD, Blu-ray, or other opticaldrive media.

Computer programs based on the written description and disclosed methodsare within the skill of an experienced developer. Various programs orprogram modules can be created using any of the techniques known to oneskilled in the art or can be designed in connection with existingsoftware. For example, program sections or program modules can bedesigned in or by means of .Net Framework, .Net Compact Framework (andrelated languages, such as Visual Basic, C, etc.), Java, C++,Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with includedJava applets.

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

What is claimed is:
 1. A computer-implemented system for stowingproducts, the system comprising: a memory storing instructions; and atleast one processor configured to execute the instructions to: receive,from a user mobile device associated with a user, a tote identifierassociated with a tote containing at least one product for stowing;predict, based on the tote identifier, a location for stowing the atleast one product contained in the tote, wherein predicting the locationfor stowing the at least one product contained in the tote comprises:receiving data from the user mobile device in one format or protocol;converting the received data into another format or protocol;determining a location of the user mobile device based on the converteddata; determining empty locations within a fulfillment center that arecapable of receiving the at least one product; and selecting, among thedetermined empty locations, an empty location closest to the location ofthe user mobile device as the location for stowing the at least oneproduct; provide, to the user mobile device, a location recommendationfor stowing the at least one product contained in the tote based on thepredicted location; receive, from the user mobile device, a productidentifier associated with the at least one product, a locationidentifier associated with a position in the predicted location at whichthe at least one product is to be stowed, and a quantity of the at leastone product to be stowed; modify a database to assign the locationidentifier and the quantity to the product identifier; receive, from theuser mobile device, a notification of a stowing error associated withthe tote identifier, the stowing error comprising at least one of anoverage or a shortage; modify the database to assign the stowing errorto the tote identifier; and automatically report the stowing error to aremote device, wherein: when the stowing error comprises overage, the atleast one processor is configured to execute the instructions to:determine a cause for the overage, the cause for the overage comprisingat least one of a product damage or a barcode damage; and provide, viathe user mobile device, a location recommendation for transferring atleast one product with at least one of the product damage or the barcodedamage; and when the stowing error comprises shortage, the at least oneprocessor is configured to execute the instructions to: request, via theuser mobile device, a difference between a physical quantity of the atleast one product and an expected quantity of the at least one product;and store the difference in the database.
 2. The system of claim 1,wherein the product identifier associated with the at least one productcomprises a stock keeping unit (SKU) associated with the at least oneproduct.
 3. The system of claim 1, wherein, when the tote identifier isscanned, the at least one processor is further configured to execute theinstructions to send a cause of the stowing error for display to theuser mobile device.
 4. A computer-implemented method for stowingproducts, the method comprising: receiving, by at least one processorand from a user mobile device associated with a user, a tote identifierassociated with a tote containing at least one product for stowing;predicting, by the at least one processor and based on the toteidentifier, a location for stowing the at least one product contained inthe tote, wherein predicting the location for stowing the at least oneproduct contained in the tote comprises: receiving, by the at least oneprocessor, data from the user mobile device in one format or protocol;converting, by the at least one processor, the received data intoanother format or protocol; determining a location of the user mobiledevice based on the converted data; determining empty locations within afulfillment center that are capable of receiving the at least oneproduct; and selecting, among the determined empty locations, an emptylocation closest to the location of the user mobile device as thelocation for stowing the at least one product; providing, by the atleast one processor and to the user mobile device, a locationrecommendation for stowing the at least one product contained in thetote based on the predicted location; receiving, by the at least oneprocessor and from the user mobile device, a product identifierassociated with the at least one product, a location identifierassociated with a position in the predicted location at which the atleast one product is to be stowed, and a quantity of the at least oneproduct to be stowed; modifying, by the at least one processor, adatabase to assign the location identifier and the quantity to theproduct identifier; receiving, by the at least one processor and fromthe user mobile device, a notification of a stowing error associatedwith the tote identifier; modifying, by the at least one processor, thedatabase to assign the stowing error to the tote identifier; andautomatically reporting, by the at least one processor, the stowingerror to a remote device, wherein: when the stowing error comprisesoverage, the at least one processor is configured to: determine a causefor the overage, the cause for the overage comprising at least one of aproduct damage or a barcode damage; and provide, via the user mobiledevice, a location recommendation for transferring at least one productwith at least one of the product damage or the barcode damage; and whenthe stowing error comprises shortage, the at least one processor isconfigured to: request, via the user mobile device, a difference betweena physical quantity of the at least one product and an expected quantityof the at least one product; and store the difference in the database.5. The method of claim 4, wherein the product identifier associated withthe at least one product comprises a stock keeping unit (SKU) associatedwith the at least one product.
 6. The method of claim 4, furthercomprising sending a cause of the stowing error for display displayingto the user mobile device.